feat(workflow): add SDK parity dispatch workflow#5
Conversation
salihguru
commented
Apr 8, 2026
salihguru
commented
- Introduced a new GitHub Actions workflow for SDK parity dispatch.
- Triggers on push and pull request events for changes in the 'lib' directory.
- Utilizes a reusable workflow from tapsilat/tapsilat-sdk-parity.
- Inherits secrets for secure operations.
- Introduced a new GitHub Actions workflow for SDK parity dispatch. - Triggers on push and pull request events for changes in the 'lib' directory. - Utilizes a reusable workflow from tapsilat/tapsilat-sdk-parity. - Inherits secrets for secure operations.
There was a problem hiding this comment.
Pull request overview
Adds a new GitHub Actions workflow to dispatch SDK parity checks whenever lib/** changes, using a reusable workflow from tapsilat/tapsilat-sdk-parity.
Changes:
- Added
sdk-parity-dispatch.ymlworkflow triggered onpush,pull_request, andworkflow_dispatch(scoped tolib/**). - Invokes a reusable workflow and inherits repository secrets for the run.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| jobs: | ||
| parity-dispatch: | ||
| uses: tapsilat/tapsilat-sdk-parity/.github/workflows/reusable-sdk-parity-dispatch.yml@main |
There was a problem hiding this comment.
The reusable workflow is referenced via @main, which is a mutable ref and can change unexpectedly (and is a supply-chain risk). Prefer pinning to a version tag or a specific commit SHA (and update periodically) so runs are reproducible and safer.
| push: | ||
| paths: | ||
| - "lib/**" |
There was a problem hiding this comment.
on.push currently triggers for matching lib/** changes on pushes to any branch. Other workflows in this repo (e.g., .github/workflows/ci.yml) restrict push triggers to main; if that’s the intended pattern here too, add a branches: filter to avoid running this workflow on every feature-branch push.
